Repository navigation
Add exact Dawn Vulkan instance query - #650
Merged
Merged
Conversation
This was referenced Sep 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The exact Dawn Vulkan query exposed the physical device, device, and queue but omitted the owning VkInstance and instance resolver. AppScene therefore could not construct an Xlib surface or Skia Graphite context in the same Vulkan instance. The v1 live-device registry also used exception handling inside Dawn's
-fno-exceptionsbuild.Change
vkGetInstanceProcAddrCloses #649.
Validation
git diff --checkpassed. This also addresses the deterministic-fno-exceptionsfailure from Graphics SDK run 35434033766. Per the current fast integration policy, builds and physical Linux qualification are deferred to CI and the AppScene host-backend lane.